rust: Fix receiving async events in busy yield loops #1439
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit fixes an issue with the rust async support where when a yield-loop was detected it suspended with
CALLBACK_CODE_YIELDwhich meant that it wasn't possible to deliver async events for other async operations in progress. The fix is to instead returnCALLBACK_CODE_POLLwith the waitable-set that has all the waitables inside of it. This enables delivery of async events from that set to ensure that if the yielding task is waiting on something else that it gets delivered.This also refactors a few things here and there, such as
CALLBACK_CODE_*, to be less error prone. Support was added for composing 3+ components withwasm-composesincewacdoesn't yet use the samewasm-tools.